internal: No std testing - #6257
Conversation
317f923 to
48421e3
Compare
c6399bf to
3ef9bca
Compare
davidhewitt
left a comment
There was a problem hiding this comment.
Thanks, looks correct to me!
|
I do now know why these changes cause the ffi-check to fail on some platforms. Please help. |
|
#6302 should have fixed, plz merge main / rebase |
abefb81 to
f882c6a
Compare
@davidhewitt done |
|
@davidhewitt I think that was a spurious issue with cargo-careful. |
|
@davidhewitt, it looks like it's not a spurious issue, but for some reason it's not finding the std that cargo-careful compiled for it. |
|
Will attempt to debug later |
|
Hoping queuing behind #6310 now lands this... |
|
@davidhewitt the latest failure was a network timeout: https://github.com/PyO3/pyo3/actions/runs/31274626505/job/93148274520#step:16:677 |
|
It looks like an inheritance test failed because references to a type were leaked. Could that have been caused by this PR? |
|
Yikes, I'm sorry CI has been so flaky here. I'll try to keep chipping away at whatever is going wrong. |
|
I think #6313 should fix once merged. |
This is part of the WIP
no_stdsupport.I am not yet working on CI as that will need a separate discussion so that maintainers can decide how it should be handled. For now, I want to locally run something like this:
I've tried making the noxfile aware of the features required forno_stdbuilds, but I am not sure I've got it quite right.